| From: | Bart King |
| Date: | 16 Apr 00 at 11:21:51 |
| Subject: | Re: OpenLibrary() snooping... |
Allan Odgaard <Duff@DIKU.DK> wrote:
> Apparently some programs forget to close the libraries they use. This sucks as
> I can't flush them later (to replace/upgrade etc.) -- I was wondering if there
> exists a tool which monitors Open & CloseLibrary(), so that it could, on
> demand, dump info about who's the sinner?
Long shot, but it might work... Try a combination of Scout and SnoopDOS.
Sure, SnoopDOS won't tell you when CloseLibrary()'s occur, but Scout tells
you the open count of libraries.
Don your detective hat and you might be able to find out, for example:
- Run the program with SnoopDOS loaded, to see what libraries it opens.
- Write these libraries down on a bit of paper or something.
- Load Scout, write down the OpenCount values of the libraries the program
opens.
- Run the program again, and quit it.
- Compare OpenCount values in Scout again.
You might be able to figure it out then. Of course, you'd have to run
SnoopDOS then Scout first, since these programs open their own libraries,
and make sure you don't run anything else :)
Maybe there is a better way, but this is what I can think of right now :)
------------------------------------------------------------------------
Whatever you want, chances are you'll find it at one of the hundreds
of sites in The PointClick Network--like Disney.com, eCost.com,
FogDog.com and many more. You get paid as you shop and an additional
10% off any purchase, anytime.
http://click.egroups.com/1/2994/1/_/451227/_/956079860/
------------------------------------------------------------------------